Skip to content

fix: point pypi-publish action to correct dist directory#2

Merged
skullydazed merged 1 commit into
mainfrom
copilot/fix-publish-binctl-client-job
Jun 7, 2026
Merged

fix: point pypi-publish action to correct dist directory#2
skullydazed merged 1 commit into
mainfrom
copilot/fix-publish-binctl-client-job

Conversation

Copilot AI commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

pypa/gh-action-pypi-publish defaults to dist/ at the workspace root, but uv build --directory binctl/binctl-client outputs to binctl/binctl-client/dist/, causing the publish step to fail with FileNotFoundError: No such file or directory: '/github/workspace/dist'.

Changes

  • publish.yml: Add packages-dir: binctl/binctl-client/dist to the PyPI publish step so the action finds the built artifacts.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes the PyPI publishing workflow by configuring pypa/gh-action-pypi-publish to upload from the actual build output directory produced by uv build --directory binctl/binctl-client, rather than the action’s default dist/ at the workspace root.

Changes:

  • Update the PyPI publish step to use packages-dir: binctl/binctl-client/dist so it can locate the built artifacts.
  • Prevent workflow failures caused by FileNotFoundError when /github/workspace/dist does not exist.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@skullydazed skullydazed merged commit df36e2f into main Jun 7, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants